-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add image overrides for CAPI/CAPRKE2 images #860
Add image overrides for CAPI/CAPRKE2 images #860
Conversation
images: | ||
- name: "cluster-api" | ||
repository: "https://github.com/rancher-sandbox/cluster-api" | ||
tag: "v1.7.7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI I figured out why the CoreProvider
override is not enough in my environment - we're following the airgapped docs and creating configmaps from the upstream manifests, we need to update the docs (and our edge airgap resources chart) to align with the forks instead
# kubectl get cm -n capi-system core-cluster-api-v1.7.7 -o yaml | grep image:
image: registry.k8s.io/cluster-api/cluster-api-controller:v1.7.7
# kubectl get deployment -n capi-system -o yaml | grep image:
image: registry.k8s.io/cluster-api/cluster-api-controller:v1.7.7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, it seems that CM is created even in the non-airgapped scenario so my analysis above may be incorrect, I still think we need to align the airgapped docs though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please check if the configMap with overrides is mounted into CAPI operator pod? If it is not, then this will not effective (meaning clusterctl-config.yaml
configMap). May happen if capi operator is not installed as a dependency of turtles within chart settings.
You don’t need to update your generated air-gap configmaps if you only need an image to point to the registry override we are specifying here, upstream manifests will work just fine. This will be performed by regular image overrides functionality implemented upstream (with a fix recently, so it should work as long as CM is mounted) and applied to all versions of manifests, even the air-gapped ones you have.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, it seems that CM is created even in the non-airgapped scenario so my analysis above may be incorrect, I still think we need to align the airgapped docs though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change should specify an override to registry image, as displayed in example kubernetes-sigs/cluster-api-operator#616 (comment)
Specifying an override tag will need a change to updatecli procedure, and may forcefully override the tag user specifies on CAPIProvider
, so it should not be set here.
09bd702
to
8dc93e8
Compare
Signed-off-by: Furkat Gofurov <[email protected]>
8dc93e8
to
0e92bda
Compare
Superseded by: #874 |
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Checklist: